Deterministic verification of digital identity documents

ABSTRACT

A method, computer program product, and system obtaining and identity verification request that include a specification for one or more electronic identity documents including one or more requested document types to fulfill the identity verification request. One or more processors locate at least one electronic identity document including each of the requested document types. Each electronic identity document in the repository includes machine readable metadata that includes the document type of that document. The one or more processors per form a deterministic match to select one electronic identity document including each of the one or more requested document types to utilize in formulating a response to the identity verification request and formulate a response to the identity verification request, based on the selected electronic identity document(s).

BACKGROUND

Documents that evidence the identity of the presenter are essential tomany common transactions and interaction. Carrying proof of identity andproof of privilege documents (e.g., driver's license, fishing license,and membership cards) can be burdensome, so the industry is exploringthe digital space. Given that different types of identification areappropriate and/or acceptable in different situations, whether digitalor physical, managing all the different types of identification,guarding one's privacy by only presenting the necessary identificationwithout extraneous personal information, as well as tracking when topresent certain, identification, becomes burdensome both for thosepresenting and evaluating credentials.

SUMMARY

Shortcomings of the prior art are overcome and additional advantages areprovided, through the provision of a computer program product forevaluating and responding, to a verification request. The computerprogram product comprises a storage medium readable by a processingcircuit and storing instructions for execution by the processing circuitfor performing a method. The method includes, for instance: obtaining,by one or more processors, an identity verification request, wherein theidentity verification request comprises a specification for one or moreelectronic identity documents comprising one or more requested documenttypes to fulfill the identity verification request; based on theobtaining, searching, by the one or more processors, a repository ofelectronic identity documents to locate at least one electronic identitydocument comprising each of the one or more requested document types,wherein each electronic identity document in the repository comprisesmachine readable metadata comprising an respective document type; basedon locating the at least one electronic identity document comprisingeach of the one or more requested document types, performing, by the oneor more processors, a deterministic match to select one electronicidentity document comprising each of the one or more requested documenttypes to utilize in formulating a response to the identity verificationrequest; and formulating, by the one or more processors, a response tothe identity verification request, based on the selected electronicidentity documents.

Shortcomings of the prior art are overcome and additional advantages areprovided through the provision of a method of evaluating and respondingto a verification request. The method includes, for instance: obtaining,by one or more processors, an identity verification request, wherein theidentity verification request comprises a specification for one or moreelectronic identity documents comprising one or more requested documenttypes to fulfill the identity verification request; based on theobtaining, searching, by the one or more processors, a repository ofelectronic identity documents to locate at least one electronic identitydocument comprising each of the one or more requested document types,wherein each electronic identity document in the repository comprisesmachine readable metadata comprising an respective document type; basedon locating the at least one electronic identity document comprisingeach of the one or more requested document types, performing, by the oneor more processors, a deterministic match to select one electronicidentity document comprising each of the one or more requested documenttypes to utilize in formulating a response to the identity verificationrequest; and formulating by the one or more processors, a response tothe identity verification request, based on the selected electronicidentity documents.

Shortcomings of the prior art are overcome and additional advantages areprovided through the provision of a system for evaluating and respondingto a verification request. The system comprises a memory, a processor incommunication with the memory, and program instructions executable bythe processor via the memory to perform a method. The method includes,for instance: obtaining, by one or more processors, an identityverification request, wherein the identity verification requestcomprises a specification for one or more electronic identity documentscomprising one or more requested document types to fulfill the identityverification request; based on the obtaining, searching, by the one ormore processors, a repository of electronic identity documents to locateat least one electronic identity document comprising each of the one ormore requested document types, Wherein each electronic identity documentin the repository comprises machine readable metadata comprising anrespective document type; based on locating the at least one electronicidentity document comprising each of the one or more requested documenttypes, performing, by the one or more processors, a deterministic matchto select one electronic identity document comprising each of the one ormore requested document types to utilize in formulating a response tothe identity verification request; and formulating, by the one or moreprocessors, a response to the identity verification request, based onthe selected electronic identity documents.

Methods and systems relating to one or more aspects are also describedand claimed herein. Further, services relating to one or more aspectsare also described and may be claimed herein.

Additional features and advantages are realized through the techniquesdescribed herein. Other embodiments and aspects are described in detailherein and are considered a part of the claimed aspects.

BRIEF DESCRIPTION OF THE DRAWING

One or more aspects are particularly pointed out and distinctly claimedas examples in the claims at the conclusion of the specification. Theforegoing and objects, features, and advantages of one or more aspectsare apparent from the following detailed description taken inconjunction with the accompanying drawings in which:

FIG. 1 is a workflow diagram depicting aspects of the present technique;

FIG. 2 illustrates certain aspects of some embodiments of the presentinvention;

FIG. 3 illustrates certain aspects of some embodiments of the presentinvention;

FIG. 4 depicts one embodiment of a cloud computing node;

FIG. 5 depicts one embodiment of a cloud computing environment; and

FIG. 6 depicts one example of abstraction model layers.

DETAILED DESCRIPTION

The accompanying figures, in which like reference numerals refer toidentical or functionally similar elements throughout the separate viewsand which are incorporated in and form a part of the specification,further illustrate the present invention and, together with the detaileddescription of the invention, serve to explain the principles of thepresent invention. As understood by one of skill in the art, theaccompanying figures are provided for ease of understanding andillustrate aspects of certain embodiments of the present invention. Theinvention is not limited to the embodiments depicted in the figures.

As understood by one of skill in the art, program code, as referred tothroughout this application, includes both software and hardware. Forexample, program code in certain embodiments of the present inventionincludes fixed function hardware, while other embodiments utilized asoftware-based implementation of the functionality described. Certainembodiments combine both types of program code.

The industry for Identity Documents (e.g., driver's licenses,recreational licenses, membership cards, etc.) is going digital. Thisdigitalization of these proof of identity (and proof of privilege, inthe case of membership) documents presents new challenges to individualsand entities who must verify the identity of an individual providingthese documents, including locating the correct card to satisfy a givenverification challenge.

Other challenges exist in the realm of verification challenges relatedto correctly supplying a document that will satisfy a verificationchallenge. For example, an out-of-state license alone may not satisfycertain verification challenges, such as those related to an individualattempting to buy age-dependent products. However, in the case of thepurchase attempt, the request could have been fulfilled with anout-of-state license in addition to additional forms of identification,which the individual has available digitally, but is unaware of whichforms of identification would satisfy the request. Also, because theindividual may possess multiple forms of digital identification,including, but not limited to, a wholesale club membership card, auniversity student identification card, a NH Fishing License, a NorthCarolina (NC) Vessel License, a political advocacy group membershipcard, a medical insurance card, and/or a property insurance card, thedriver is at a loss regarding which digital document to provide to meetthe requirements of the specific challenge.

Beyond providing a document that meets the requirements of a specificidentity challenge, there are also privacy concerns that pervade,especially when so much personal information is readily available andonly a small subset is required, and, depending on the age of the driver(or other individual proving his or her identity), legally obtainable.For example, a given merchant may require a driver's license for a giventransaction but does not need all the attributes, since that wouldprovide privacy information not needed apart from, depending on theproduct being purchased, information that the buyer is over a given ageand that the buyer resembles the photograph on the license.

Additional complications in presenting and verifying identification mayalso occur when an institution requires more than one form ofidentification. For example, a pharmacy may require a driver's license,and insurance card, and possibly a further form of identification (e.g.,a medical insurance card) by law. Time is wasted when an individual mustfumbled through all of his or hers digital cards to fill a request to anauthority, including checking which cards to send or show.

There is a need to programmatically streamline, in an intelligentmanner, the verification of digital documents, in a mariner that iscompatible with the process of the creating these digital documents.There is also a need for a digital identification verification systemthat support deterministic match capabilities. Certain embodiments ofthe present invention address both of these challenges.

An advantage of certain embodiments of the present invention in that itprovides a verification of the identity of an individual. By allowing aflexible and electronic verification of identification, embodiments ofthe present invention improve existing computer technology by addressinginformation privacy concerns while enabling a more efficientverification process, therefore improving the functionality of computingsystems, even in environments that require heightened security.

Some embodiments of the present invention may include one, or more, ofthe following features, characteristics, operations and/or advantages:(i) an electronic identity document that is characterized by a “type”(e.g., driver's license, fishing license, membership card, insurancecard, rewards card, social security card, police badge, card for foodassistance, library card, gym membership, etc.), where the electronicidentity document file includes machine readable metadata indicating the“type” of electronic identity document); (ii) a matching mechanism thatuses the type metadata of the document to determine which among a set ofowner's documents should be used as a response to a verificationscenario; (iii) the ability to determine, by machine logic, whichdocument should be used in a verification scenario (verifying the datathat is on the document in some way , and (iv) allows a verifier torequest one or more documents, each of a specific type (or sub-type orsub-sub-type, etc. in a hierarchical type definition scheme), and theowner's device can automatically match which documents fulfill theverifier's request. Further with respect to item (iv) on the foregoinglist, for example, a pharmacist might ask to see two forms of governmentpicture identification and an insurance card from someone picking up aprescription. The verifier (the pharmacist) can request two documents,both of the document category “government identification”, and a thirddocument of category “medical insurance”. Machine logic of someembodiments of the present invention provide for automatic (that is,without substantial human intervention) matching of an owner's documentsto determine which are government issued documents, out of a set thatcould include a driver's license, grocery store card, gym membership,vehicle registration, passport, student id, etc. Multiple documents suchas the driver's license, passport and student id have portraits of theowner, but only the driver's license and passport would act as a validgovernment issued document in this example.

In an embodiment of the present invention, an electronic identitydocument is characterized by a “type” by including a “document type”value in a file that comprises an electronic identity document machinereadable metadata. Certain types of documents belong to certaincategories that are represented by these document types. A givendocument type may represent a category of document, including but notlimited to, a driver's license, fishing license, membership card,insurance card, rewards card, social security card, police badge, cardfor food assistance, library card, gym membership, etc. Thus, electronicidentity document file includes machine readable metadata comprising thedocument type of the electronic identity document.

Embodiments of the present invention also include a method for an ownerto fulfill a request from a verifier for identifying information byusing one or more categories of documents designated with differentdocument types. In an embodiment of the present invention, theindividual identity documents may include attributes and a verificationchallenge may require a response including these attributes, which theprogram code, in an embodiment of the present invention, may ascertainfrom one or more identity documents retained in a memory accessible to aclient computing device. In an embodiment of the present invention, averifier can request information by specifying document categories(characterized by metadata comprising document types in the files) andattributes for each category of document necessary to validate theidentity of the owner.

In an embodiment of the present invention, program code generatesidentity documents that each include document types, i.e., machinereadable metadata indicating a category of the electronic identitydocument in each file representing an individual identity document. Asexplained below, in an embodiment of the present invention, the programcode utilizes the document type of a given electronic document file todetermine whether the contents of the file satisfy a givenidentification verification challenge. In an embodiment of the presentinvention, the addition of a document type to a file representing anidentity document enables support for the program code to provide adeterministic match capability. To further enhance user experience, theprogram code may store, in a memory resource, a definition for eachdocument type in a document definition, which can be accessed by theprogram code and provided to a user of a client computing node in agraphical user interface, enhancing the user experience. The definitionmay include plain text describing the categories of documentsrepresented as various (metadata-based) document types. Thus, a documentdefinition for a given document type may map a category to the documenttype. In an embodiment of the present invention, categories embedded orencoded as (metadata) document types in electronic identity documentsinclude, but are not limited to: government identification, driver'slicense, student identification, rewards card, vehicle insurance, healthinsurance, membership card.

FIG. 1 is overview that depicts various aspects of an embodiment of thepresent invention. FIGS. 2-3 are workflows that highlight aspects ofvarious embodiments of the present invention from the point-of-view ofprogram code making a verification request and receiving a response,e.g., FIG. 2, and from the point of view of program code obtaining averification request and formulating a response, e.g., FIG. 3. Aspectsof FIG. 2 and FIG. 3 can be accomplished by program code executed by thesame processor or a group of processors. The two points of view aremerely presented for illustrative purposes.

Returning to FIG. 1, in an embodiment of the present invention, a firstcomputing node 110 communicates a verification request 115 to a secondcomputing node 120. As an example, program code comprising theverification request 115 may include a request for a document of aspecific category, and therefor with a specific document type, tofulfill, for example, a basic proof of identity. The program code thatcomprises the verification request 115 may also specify certainattributes that satisfy the verification, in addition to the documenttype, such as, name portrait (picture of the individual being identifiedtaken by the issuing authority), and an expiration date for theelectronic identity document.

In an embodiment of the present invention, program code creates eachidentity document with defining attributes and a document type. Thedocument type may represent a category of document that includes, but isnot limited to, a driver's license, fishing license, membership card,insurance card, rewards card, social security card, police badge, cardfor food assistance, library card, and gym membership. Files thatcomprise the identity documents include these document types as machinereadable metadata. The document type of a file and the attributes of thefile may be utilized in verifications by embodiments of the presentinvention. The attributes may be tagged with an ISO specifiedidentifiers (e.g., ISO, WEDI and/or custom) which can be used to matchindividual attributes at a granular level. The categories of documentsrepresented by various document types can be understood as part of anecosystem framework for matching at a macro level in response toidentification challenges.

As illustrated in FIG. 1, the program code at the second computing node110 receives the verification request 115, and identifies which digitalidentity documents satisfy the verification request 115. In anembodiment of the present invention, the digital documents 125 that theprogram code could utilize to respond to the request are stored in amemory 130 on the second computing node 120 itself. In this embodiment,the second computing device 120 does not utilize a backend databaseoutside of the second computing device 120 itself in order to maintainthe security of the digital documents. In an embodiment of the presentinvention, the program code executed by one or more processorsaccessible to the second computing device 120 locally encrypts theidentity documents that it stores, for example, using a public keyspecific to the second computing device 120 In an embodiment of thepresent invention, program code executed on the second computing device120 stores the identity documents in an area and/or manner that is notaccessible to any other applications executing on the second computingdevice 120 and/or otherwise utilizing resources of the second computingdevice 120.

In an embodiment of the present invention, a document type for a givendigital document may logistically represent more than one category ofdigital document. In an embodiment of the present invention, eachdocument category is in a tree hierarchy, thus, for example, a driver'slicense is in the branch of government identification. The document typein this case would be assigned category “driver's license” and by natureof the tree hierarchy of categories is also identifiable as a governmentid by the program code. By utilizing this tree hierarchy to effectivelyenable a document type (e.g., metadata in the electronic file comprisingthe electronic identity document) to encompass more than one category ofidentification, the program code performing a deterministic match basedon a verification request can utilize a digital identification in aresponse that meets the criteria in a verification request, which, inturn, enables accurate verification based on the same digital documentboth in a scenario where verifier only needs basic proof of identity, aswell as, for example, at traffic stop scenario, where a law enforcementofficer needs to specifically cheek for a valid driver's license.

Depending upon the embodiment of the present invention, communicating averification request 115 from the first computing node 110 to the secondcomputing node 120 may be performed in a variety of different ways topreserve the security of the identity documents utilized to respond tothe verification request 115. For example, in an embodiment of thepresent invention, program code executed by one or more processorsaccessible to the first computing node 110 may broadcast theverification request 115 and program code executed by one or moreprocessors accessible to the second computing device 120 may obtain theverification request 115 and display the verification request 115 in adisplay communicatively connected to the one or more processorsexecuting, the program code A user of the second computing node 120 mayutilize the display or another input/output device of the secondcomputing node 120 to accept the verification request 115. When theprogram code receives the acceptance of the user, the program coderesponds to the verification request 115. If the program code receives adenial of the verification request, or, for example, no response fromthe user after a certain amount of time has lapsed, the program codewill not respond to the verification request 115 with proof of identity.In another embodiment of the present invention, the program code thatreceives the request for verification 115 may vet the sender andautomatically respond to the verification request 115 based onascertaining information about the sender.

As understood by one of skill in the art, when a connection is enabledbetween the first computing device 110 and the second computing device120, program code originating from each device may execute on the otherdevice as part of the verification process. Thus, although FIG. 1depicts a request 115 from program code at the first computing device110 and a response 135 from a second computing device 120, the methodmay vary insofar as the originator of the program code in accordancewith various embodiments of the present invention.

Returning to FIG. 1, program code at the second computing device 120obtains the verification request 115 and formulates a response 135 basedon the verification request 115 and the digital documents 125 (storedlocally, in this embodiment) in a memory 130. As illustrated in FIG. 1,more than one identify document may satisfy a given verification request115. As aforementioned, the verification request 115 in this examplerequested an identity document of a given document type with name,portrait, and expiration date attributes. Program code responds to theverification request 115 by locating, in this example, more than oneidentity document of the digital documents 125 stored in the memory 130that satisfy the verification request 115. In this example, both adriver's license and a passport include the requested document type, butonly the driver's license include all of attributes and are associatedwith the category of document requested.

In an embodiment of the present invention, administrators may define thecategories of document that will be represented by certain documenttypes in electronic files representing the documents. Thus, program codeperforming aspects of the verification process described herein mayaccess these pre-defined mappings. These document categories, which aremapped to document types, can be understood as levels of verification,such that multiple verification entities may use the same document in aresponse and be guaranteed accuracy. Including document types in digitaldocuments establishes a level of verification that differentiates whichdigital documents can be used for certain verification scenarios. Forexample, verification scenarios that require a government issuedidentification document could be differentiated from those that requireany non-official proof of name and photo.

In an embodiment of the present invention, associating new kinds ofdocuments with certain categories of digital documents with givendocument types may require approval by an account representative, asthis association will be utilized by many different entities who verifyidentity and should be accurate across all verification scenarios. Whileassigning a document type corresponding to a low-security identificationdocument, for example to a document that can be categorized as a retailrewards card, may not require great scrutiny, associating identificationfrom a country outside of the United States with a government-issuedidentification document type could require greater scrutiny. Thus, in anembodiment of the present invention a property can be defined for eachdocument type to mark whether or not adding this document type to a newkind of digital document, requires approval. For example, adding adocument type used to identify/categorize documents as government-issuedidentification to a new kind of document could be approved only forissuers that have been confirmed to issue government identificationdocuments, while adding a document type used to identify/categorizemembership cards for a generic business to a kind of document would notrequire this approval.

Returning to FIG. 1, in an embodiment of the present invention, eitherthe owner or the program code selects a single document from thedocuments that satisfies the Verification request 115 to be included ina response 135. FIG. 1, only one document, the driver's license, is adirect response to the verification request 115. Thus, the program codecan make the selection automatically, but if more than one documentsatisfied the verification request, the program code could solicit inputfrom a user and/or could select which document to utilize in theresponse 135 based on pre-defined criteria.

In an embodiment of the present invention, the program code generates aresponse 135 based on selecting the document. By supplying only theminimum amount of information requested by the verification request 115to satisfy the request, the program code protects the privacy of theowner of the digital documents 125. In an embodiment of the presentinvention, the program code may select a document from two documentsthat fulfill the request based on an algorithm weighting certaindocuments above others. As illustrated in FIG. 1, the response 135, inan embodiment of the present invention, includes the categoryrepresented by the document type and attributes.

Upon receipt of the response 135 by the first computing device 110, inan embodiment of the present invention, the program verifies that theresponse 135 matches the verification request 115. For example, theprogram code verities that the response 135 contains a document type andattributes that the verification request 115 included. If there is anexact match between the verification request 115 and the response 135(i.e., the attributes that were provided were from a document with thedocument type of the document specified in the request and theattributes were those requested), the verification transaction betweenthe first computing device 110 and the second computing device 120 iscomplete, and the identity is verified. If the program code cannotverify the response 135, the identity of the owner is not verified.

There exist many situations where embodiments of the present inventionmay verify the identity of an individual when a human would not be ableto make the verification. For example, an individual may desire toobtain a product where the law requires that the buyer be of a minimumage and the buyer must be able to present a government-issuedidentification in order to prove that he or she meets the minimum agerequirement. This particular buyer, however, does not have a UnitedStates Government-issued identification document, but is only inpossession of a government-issued identification document from his orher country of origin, for example, Denmark. This document is evidencethat this individual exceeds the minimum age for purchase of theproduct. A clerk charged with verifying the age of product purchasersbefore allowing the purchase is both unfamiliar-with the appearance ofan identification issued by the government of Denmark and unable tocomprehend the language on the identification, Danish. Thus, the clerkcannot verify the identity of the individual in order to make the sale.However, utilizing an embodiment of the present invention, this clerkwould be able to accurately verify the identity of the individual andmake the sale.

Utilizing an embodiment of the present invention, the clerk, forexample, in possession of the first computing, device 110, couldbroadcast a verification request 115 to a device utilized by thecustomer, e.g., the second computing device 120. The verificationrequest 115 would include a document type corresponding to thegovernment-issued identification category and an attribute of date ofbirth. The verification request 115 would also specify that the date ofbirth should be within certain parameters complying with the minimumage. The second computing device 120 would accept the request andprogram code would match the document type specified in the verificationrequest 115 to a digital document with the same document type (i.e., adocument in the government-issued identification category) accessible tothe second computing device 120, in this case, the purchaser'sgovernment-issued identification from Denmark. The program code wouldsearch the attributes of this digital document to locate a date of birthand determine whether the date of birth is within the parametersspecified in the verification request 115. The program code would issuea response 135 from the second computing device 120 to the firstcomputing device 110 comprising the document type and the date of birthattribute. The response 135 may also include information furtheridentifying the document that provided the source for this information,for example, that the document is a government-issued identificationfrom Denmark.

Upon receipt of the response 135, program code will verify that theresponse 135 comports with the request. In embodiments of the presentinvention, by utilizing program code to generate a response 135 based onan initial request 115 and then verifying that the response 135satisfies the request 115 the program code that performs the finalverification serves as an added later of security. Thus, in thisexample, the clerk utilizes an embodiment of the present invention toverify the customer's identity and to verify that the customer iseligible to purchase the product, which was not possible withoututilizing aspects of an embodiment of the present invention.

In an embodiment of the present invention, the verification request 115may include a request for more than one category of document electronicdocuments with different document types) in an embodiment of the presentinvention, program code requests documents matching one or moredocuments types in a verification request 115. For each document typerequested, the verification request 115 may include one or moreattributes. Program code fulfills this verification request 115 andformulates a response 135 using data from documents matching thedocument types sped tied in the verification request 135. To that end,the program code builds a response 135 from documents and attributesthat have been defined with document types specified in the verificationrequest 115. Attributes in the response 135 are associated with thecategory of the document (identified by the program code by documenttype), ensuring that identity information from a valid source is used.In an embodiment of the present invention, the response 135 may includeany unfulfilled requirements of the request. The program code displaysthese shortcomings to a user for further manual verification. Inembodiments of the present invention, matching information can betrusted to be accurate based on the specification of document types fromwhich it is provided.

FIG. 2 is a workflow 200 that illustrates certain aspects of anembodiment of the present invention and specifically program codegenerating a verification request 115 (e.g.. FIG. 1) and verifying aresponse 135 (e.g., FIG. 1). In an embodiment of the present invention,program code issues a verification request that includes a document typeidentifying one or more category of digital identity document that wouldsatisfy the verification request (210). The verification request mayalso include at least one attribute, where the attribute is a parameterspecific to the request that the program code is requesting, and theattribute is present on a digital document utilized to respond to theverification request.

Based on the request, the program code receives a response (220). In anembodiment of the present invention, the response includes an identifierof a digital document and the category or document type associated withthe digital document. The response may also include one or moreattributes from the document that were included in the initial request.Based on receiving the response, the program code verifies that theresponse satisfies the request, including whether the document type ofthe responsive document identified in the request matches the documenttype in the response (230). If the program code verifies the request,the identity verification transaction is complete (240). In anembodiment of the present invention, the program code may notify theuser that the identification was successful (250 a). If the program codecannot verify the identity based on the response (240), for example, theresponsive document did not include the document type requested, theprogram code may alert an operator of the computing device making theverification that the identification was unsuccessful (250 b). Inanother embodiment of the present invention, based on the verificationfailing, the program code may automatically generate a new verificationrequest.

As discussed earlier, more than one category of document can berepresented by a document type (i.e., metadata in a file comprising anelectronic identity document). The use of document type to representthese categories may allow for a deterministic match to be computed in alarge number of cases. For example, digital documents from two differentissuers have the potential to create a verification issues at a trafficstop, e.g., the verifier request a New York State Driver's License, butthe driver has a New Hampshire Driver's License. This mismatch case oftwo different issuers in the scenario of a traffic stop is solved by theprogram code requesting a document with a document type that indicatesthat it is a driver's license, rather than trying to match attributesand asking for a specific document based on a role, and subsequentlygetting a response back that is based on similar attributes, or on therequested attributes but from a digital document in a category otherthan requested, and is therefore not fully responsive to the request. Incases such as this driver's license challenge, a law enforcement officerwill need the ability to validate an out of state license. Thus, inembodiments of the present invention, by including types, allforeseeable challenge scenarios and can be accommodated even inscenarios where issuers of digital documents are not known to theverifying authority.

In an embodiment of the present invention, as issuer would have theability to request that its digital documents be recognized and verifiedin response to verification requests. Thus, issuers would request thatits documents be included in a category that is represented in digitaldocument files in the present invention by a given document type. Forexample, the Island of Guam may request that its new governmentidentification be considered a driver's license and a governmentidentification.

FIG. 3 also illustrates a workflow 300 of an embodiment of the presentinvention but focuses on program code formulating a response 135 (e.g.,FIG. 1) to a verification request 115 (e.g., FIG. 1). In an embodimentof the present invention, program code obtains a verification request(310) that includes a document type identifying one or more category ofdigital identity document that would satisfy the verification request.The verification request may also include at least one attribute wherethe attribute is a parameter specific to the request that the programcode is requesting is present on a digital document utilized to respondto the verification request. In an embodiment of the present invention,the program code may verify that the request is from a trusted sourcebefore responding to the request.

In an embodiment of the present invention, based on obtaining thisrequest, the program code searches digital documents stored in memory tocompute a deterministic match to the verification request (320). Forexample, the program code locates digital documents where the filescontain the same document type as requested and searches the digitaldocuments for the attributes in the documents identified as includingthe particular document type. In an embodiment of the present invention,based upon an algorithm, which may be included in the request, theprogram code selects a document for use in responding to the request.

In embodiment of the present invention, responding to a verificationrequest may be automatic and handled by the program code, or the programcode may solicit input from the user (i.e., the owner of the digitaldocuments) before responding the verification request. For example, inan aspect of an embodiment of the present invention, the program codemay display to the user in a display on a computing device a list ofdigital documents that are in categories that are designated utilizingthe requested document type. The user can then select a document toutilize in responding to the request. In an embodiment of the presentinvention, the program code could offer the user the option of selectinga document outside that list as well and would guide the user intopicking this applicable document immediately and easily. For example, inan embodiment of the present invention, the program code could generatea list of documents that the program code could acquire and utilize torespond to the verification challenge. This document acquisition listcould be arranged by document categories. The user could scroll throughthis list and view which businesses have signed up as issuers and madedocuments available. A user may recognize a grocery store where he orshe has an account and could select this issuer, prompting the programcode to contact the identified issuer and download the digital identitydocument of the user from that issuer.

An embodiment of the present invention may also include an option forthe user to enable automatic responses with guaranteed accuracy frommatching document types. Embodiments of the present invention could alsoinclude an option of enabling manual controls when the program code isunable to locate a match and would interact with the user to utilize adocument that is not an exact match (e.g., a document that includes therequested documents but is from a category that is not mapped to therequested document type) to attempt to meet the verification challengeof the request.

Returning to FIG. 3, in an embodiment of the present invention, theprogram code formulates a response to the request (330). The responsemay include identifying information related to the digital documentselected for the response and it may also include the one or morecategories of the document and the content of the one or more attributerequested in the verification request.

One or more aspects may relate to cloud computing. For example, inembodiments of the present invention, the program code can accessaforementioned acquisition list that may be displayed to a user from anode of a cloud computing system and/or as the acquisition list isupdated, it can be distributed over devices that connect to the cloudcomputing node. Additionally, in an embodiment of the present invention,issuers may utilize nodes of a cloud computing system to distributeidentity documents to individual devices, enabling the devices toencrypt and store relevant documents locally. Finally, individualdevices making and responding to verification challenges can utilize acloud computing environment as a centralized source of approved issuersand categorization of documents into approved types utilized by theprogram code in both forming and responding to verification requests.

As illustrated in FIGS. 1-3, aspects of embodiments of the presentinvention include one or more processors obtaining an identityverification request, where the identity verification request includes aspecification for one or more electronic identity documents includingone or more requested document types to fulfill the identityverification request. Based on obtaining the request one or moreprocessors search a repository of electronic identity documents tolocate at least one electronic identity document including each of theone or more requested document types, where each electronic identitydocument in the repository comprises includes a document type comprisedof machine readable metadata. Based on locating the at least oneelectronic identity document comprising each of the one or morerequested document types, the one or more processors perform adeterministic match to select one electronic identity document includingeach of the one or more requested document types to utilize informulating a response to the identity verification request. The one ormore processors formulate a response to the identity verificationrequest, based on the selected electronic identity documents. In anembodiment of the present invention, the one or more processor mayperform the deterministic match automatically.

In an embodiment of the present invention, the respective type of eachelectronic identity document characterizes the electronic identitydocument.

In an embodiment of the present invention the respective types of eachelectronic identity document indicate that the document is one of adriver's license, a fishing license, a membership card, an insurancecard, a rewards card, a social security card, a police badge, a card forfood assistance, a library card, or a gym membership.

In an embodiment of the present invention, the identity verificationrequest also includes a specification for attributes of the one or moreelectronic identity documents of the one or more requested documenttypes, and where performing the deterministic match includes the one ormore processors verifying that data in each of the one electronicidentity document including each of the one or more requested documenttypes includes the attributes. In an embodiment of the presentinvention, the response includes this data from the selected electronicidentity documents.

In an embodiment of the present invention, the one or more processorobtains an identity verification request that also includes aspecification for attributes for each of the one or more electronicidentity documents of the one or more requested document types. Thus,when the one or more processor performs a deterministic match, the oneor more processors select each of the one electronic identity documentincluding each of the one or more requested document types from morethan one electronic identity document of the one or more requesteddocument types including the attributes.

In an embodiment of the present invention, the one or more requesteddocument types include at least one of: a sub-type or a sub-sub-type ina hierarchical type definition scheme.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing, is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows;

Software as a Service (SaaS); the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations), it may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forloadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 4, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 4, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”) Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples include, but are not limited to microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 5, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 5 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 6, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 5) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 6 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes 61; RISC(Reduced instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65, and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow, which may include maintaining VPD at a VPD location the computersystem. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and synchronization of identificationdocument categorization and approved issuers among client devices withconnectivity to a cloud computing node.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto a.computer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

In addition to the above, one or more aspects may be provided, offered,deployed, managed, serviced, etc. by a service provider who offersmanagement of customer environments. For instance, the service providercan create, maintain, support, etc. computer code and/or a computerinfrastructure that performs one or more aspects for one or morecustomers. In return, the service provider may receive payment from thecustomer under a subscription and/or fee agreement, as examples.Additionally or alternatively, the service provider may receive paymentfrom the sale of advertising content to one or more third parties.

In one aspect, an application may be deployed for performing one or moreembodiments. As one example, the deploying of an application comprisesproviding computer infrastructure operable to perform one or moreembodiments.

As a further aspect, a computing infrastructure may he deployedcomprising integrating computer readable code into a computing system,in which the code in combination with the computing system is capable ofperforming one or more embodiments.

As yet a further aspect, a process for integrating computinginfrastructure comprising integrating computer readable code into acomputer system may be provided. The computer system comprises acomputer readable medium, in which the computer medium comprises one ormore embodiments. The code in combination with the computer system iscapable of performing one or more embodiments.

Although various embodiments are described above, these are onlyexamples. For example, computing environments of other architectures canbe used to incorporate and use one or more embodiments. Further,different instructions, instruction formats, instruction fields and/orinstruction values may be used. Many variations are possible.

Further, other types of computing, environments can benefit and be used.As an example, a data processing system suitable for storing and/orexecuting program code is usable that includes at least two processorscoupled directly or indirectly to memory elements through a system bus.The memory elements include, for instance, local memory employed duringactual execution of the program code, bulk storage, and cache memorywhich provide temporary storage of at least some program code in orderto reduce the number of times code must be retrieved from bulk storageduring execution.

Input/Output or 110 devices (including, but not limited to, keyboards,displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives andother memory media, etc.) can be coupled to the system either directlyor through intervening I/O controllers. Network adapters may also becoupled to the system to enable the data processing system to becomecoupled to other data processing systems or remote printers or storagedevices through intervening private or public networks. Modems, cablemodems, and Ethernet cards are just a few of the available types ofnetwork adapters.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used herein, thesingular forms “a”, “an” and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willbe further understood that the terms “comprises” and/or “comprising”,when used in this specification, specify the presence of statedfeatures, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, steps, operations, elements, components and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below, if any, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of one or more embodiments has been presentedfor purposes of illustration and description, but is not intended to beexhaustive or limited to in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain variousaspects and the practical application, and to enable others of ordinaryskill in the an to understand various embodiments with variousmodifications as are suited to the particular use contemplated.

1. A system, comprising: a repository configured to store a plurality ofdigital identity documents; an interface configured to receive averification request, wherein the request includes a document typeidentifying a category that satisfies the verification request; aprocessor configured to; determine whether a digital identity documentof the plurality of digital identity documents stored in the repositoryare a match to the document type identifying the category of digitalidentity document that satisfy the verification request; in response todetermining that the digital identity document of the plurality ofdigital identity documents stored in the repository match the documenttype identifying the category of the digital identity document thatsatisfies the verification request, provide a success notification inresponse to the verification request; and in response to determiningthat the digital identity document of the plurality of digital identitydocuments stored in the repository do not match the document typeidentifying the category of the digital identity document that satisfiesthe verification request, provide an unsuccessful notification inresponse to the verification request.
 2. The system of claim 1, whereinstoring the digital identity document includes storing the digitalidentity document with an associated metadata indicating the documenttype.
 3. The system of claim 1, wherein storing the digital identitydocument includes encoding the digital identity document.
 4. The systemof claim 3, wherein the encoding uses a key.
 5. The system of claim 4,wherein the key comprises a key associated with the device whichincludes the repository.
 6. The system of claim 1, wherein the documenttype represents more than one category of digital identity document. 7.The system of claim 6, wherein the one category of digital identitydocument is one of a plurality of document categories, and wherein eachdocument category of the plurality of document categories is in a treehierarchy.
 8. The system of claim 1, wherein the document type comprisesa type, a sub-type, or a sub-sub-type within a hierarchical typedefinition scheme.
 9. The system of claim 1, wherein determining whethera digital identity document of the plurality of digital identitydocuments stored in the repository are a match to the document typeidentifying the category of digital identity document that satisfy theverification request includes searching to locate the digital identitydocument.
 10. The system of claim 1, wherein determining whether adigital identity document of the plurality of digital identity documentsstored in the repository are a match to the document type identifyingthe category of digital identity document that satisfy the verificationrequest includes verifying data of the digital identity document. 11.The system of claim 1, wherein the verification request includes aspecification for attributes.
 12. The system of claim 11, wherein thedetermining whether a digital identity document of the plurality ofdigital identity documents stored in the repository are a match to thedocument type identifying the category of digital identity document thatsatisfy the verification request includes verifying that data of thedigital identity document includes the attributes.
 13. The system ofclaim 1, wherein the digital identity document comprises one of thefollowing: identity document comprises one of: a government-issuedidentification, a passport, a driver's license, a recreation license, afishing license, a membership card, a wholesale club membership club, auniversity student identification card, a vessel license, a medicalinsurance card, an insurance card, a rewards card, a social securitycard, a police badge, a card for food assistance, a library card, or agym membership.
 14. The system of claim 1, wherein the processor isfurther configured to build a response to the verification request. 15.The system of claim 14, wherein the response to the verification requestincludes the digital document that matches the document type andattributes.
 16. The system of claim 15, wherein the attributes areassociated with a category of the document, wherein the category isidentified using the document type.
 17. The system of claim 14, whereinthe response includes an indication of an unfulfilled requirement of therequest.
 18. The system of claim 17, wherein the indication of theunfulfilled requirement of the request is displayed to a user forverification.
 19. A method, comprising: storing, in a repository, aplurality of digital identity documents; receiving, using an interface,a verification request, wherein the request includes a document typeidentifying a category that satisfies the verification request;determining, using a processor, whether a digital identity document ofthe plurality of digital identity documents stored in the repository area match to the document type identifying the category of digitalidentity document that satisfy the verification request; in response todetermining that the digital identity document of the plurality ofdigital identity documents stored in the repository match the documenttype identifying the category of the digital identity document thatsatisfies the verification request, providing a success notification inresponse to the verification request; and in response to determiningthat the digital identity document of the plurality of digital identitydocuments stored in the repository do not match the document typeidentifying the category of the digital identity document that satisfiesthe verification request, providing an unsuccessful notification inresponse to the verification request.
 20. A computer program productembodied in a non-transitory computer readable medium and comprisingcomputer instructions for: storing, in a repository, a plurality ofdigital identity documents; receiving, using an interface, averification request, wherein the request includes a document typeidentifying a category that satisfies the verification request;determining whether a digital identity document of the plurality ofdigital identity documents stored in the repository are a match to thedocument type identifying the category of digital identity document thatsatisfy the verification request; in response to determining that thedigital identity document of the plurality of digital identity documentsstored in the repository match the document type identifying thecategory of the digital identity document that satisfies theverification request, providing a success notification in response tothe verification request; and in response to determining that thedigital identity document of the plurality of digital identity documentsstored in the repository do not match the document type identifying thecategory of the digital identity document that satisfies theverification request, providing an unsuccessful notification in responseto the verification request.